Brake/drive force control system

ABSTRACT

A brake/drive force control system includes: a requested acceleration calculating section; a powertrain control section calculating a minimum brake/drive force at the time of no fuel cut and a fuel-cut brake/drive force, generating larger one of a requested brake/drive force and the minimum brake/drive force when the requested brake/drive force is larger than the fuel-cut brake/drive force, and generating the fuel-cut brake/drive force when the requested brake/drive force is equal to or smaller than the fuel-cut brake/drive force; a brake control section generating a requested brake force; and a brake/drive force control section calculating the requested brake/drive force from requested acceleration, requesting the powertrain control section for the requested brake/drive force, acquiring the brake/drive force generated by a powertrain, and when the requested brake/drive force is smaller than the acquired brake/drive force, requesting the brake control section for a difference between the requested brake/drive force and the acquired brake/drive force.

INCORPORATION BY REFERENCE

The disclosure of Japanese Patent Application No. 2019-015584 filed onJan. 31, 2019 including the specification, drawings and abstract isincorporated herein by reference in its entirety.

BACKGROUND 1. Technical Field

The disclosure relates to a brake/drive force control system that ismounted on a vehicle to control a brake/drive force of the vehicle.

2. Description of Related Art

On vehicles in recent years, a driver assistance system that is referredto as adaptive cruise control (ACC), an adjustable speed limiter (ASL),a cruise control system (CRC), or the like and has a function ofautomatically maintaining a vehicle speed is mounted. Such a driverassistance system generates and outputs an instruction to achieve andmaintain a target vehicle speed on the basis of information that isacquired from a camera, a vehicle speed sensor, and the like. With suchan instruction, a powertrain and a brake are controlled, which causesthe powertrain to generate a brake/drive force that is either a brakeforce or a drive force and the brake to generate the brake force. As aresult, the target vehicle speed is achieved and maintained.

In the case where a positive direction of the brake/drive force is setto an advancing direction of the vehicle and, for example, the vehiclemaintains the constant vehicle speed while traveling on a downhill road,the powertrain is requested to reduce the brake/drive force, and thusengine braking is expected. When the brake/drive force requested to thepowertrain becomes smaller than the brake/drive force that can only beachieved with an engine fuel cut, a fuel cut occurs. When the fuel cutoccurs, the brake/drive force generated by the powertrain is reduceddiscontinuously, falls below the brake/drive force requested to thepowertrain. As a result, the vehicle is decelerated. Meanwhile, when thebrake/drive force requested to the powertrain is increased to acceleratethe vehicle, the fuel cut no longer occurs. However, cancellation of thefuel cut leads to generation of the brake/drive force that is largerthan the brake/drive force requested to the powertrain. Just asdescribed, in the case where the constant vehicle speed is maintained onthe downhill road or the like, the execution and the cancellation of thefuel cut are repeated, which possibly causes hunting in which thebrake/drive force generated by the powertrain is abruptly reduced orincreased between a fuel-cut brake force, which is the brake forceduring the execution of the fuel cut, and a minimum brake/drive force,which is the minimum brake/drive force at the time of no fuel cut. As aresult, ride quality is possibly degraded.

In Japanese Patent Application Publication No. 2016-61179 (JP 2016-61179A), it is disclosed to prohibit the fuel cut in the case where theoccurrence of the hunting is detected during control for causing thepowertrain to generate the requested brake/drive force that is requestedto maintain the target vehicle speed.

SUMMARY

A description will be made on a problem of a method for suppressinghunting with reference to FIG. 5. Such a method is executed when it isdesired to maintain the target vehicle speed. In the method, when thehunting is detected as described above, the fuel cut is suppressed, soas to suppress the hunting. FIG. 5 includes graphs that have time in ahorizontal axis and have, on a vertical axis, an actual vehicle speed,the requested brake/drive force to the power train, and an actualbrake/drive force generated by the powertrain. The above-describedhunting occurs until time T0. After the hunting is detected, the fuelcut is suppressed between the time T0 and T1, and thus the hunting canbe suppressed. However, in this period, since the actual brake/driveforce is larger than the requested brake/drive force, the vehicle speedis increased. In order to suppress deviation of the actual vehicle speedfrom the target vehicle speed, the fuel cut is executed between the timeT1 and T2 so as to decelerate the vehicle. Thereafter, the execution andthe cancellation of the fuel cut is repeated. Just as described, simplysuppressing the fuel cut to suppress the hunting substantially means toextend cycles of the execution and the cancellation of the fuel cut byincreasing an allowable range of the deviation of the actual vehiclespeed from the target vehicle speed. In addition, suppressing the fuelcut through the detection of the hunting means that the hunting, whichoccurs firstly, cannot be avoided. Thus, there is still room forimprovement in pursuance of the target vehicle speed and in the ridequality.

The disclosure has been made in view of the above problem, and thereforehas a purpose of providing a brake/drive force control system capable ofachieving preferred pursuance of a target vehicle speed and preferredride quality in control for generating a brake/drive force in a vehiclein order to maintain the target vehicle speed.

In order to solve the above problem, an aspect of the disclosure is abrake/drive force control system that controls a brake/drive force to begenerated by a powertrain including an engine and a brake force to begenerated by a brake, so as to maintain a target vehicle speed. Thebrake/drive force control system includes: a requested accelerationcalculating section that calculates requested acceleration asacceleration generated in the vehicle to maintain the target vehiclespeed; a powertrain control section that calculates a minimumbrake/drive force, which is a minimum brake/drive force capable of beinggenerated by the powertrain without executing a fuel cut of the engine,and a fuel-cut brake/drive force, which is the brake/drive forcegenerated by the powertrain through execution of the fuel cut, accepts arequest to generate the brake/drive force, causes the powertrain togenerate larger one of the requested brake/drive force and the minimumbrake/drive force when the requested brake/drive force is larger thanthe fuel-cut brake/drive force, and causes the powertrain to generatethe fuel-cut brake/drive force when the requested brake/drive force isequal to or smaller than the fuel-cut brake/drive force; a brake controlsection that accepts a request to generate the brake force and causesthe brake to generate the requested brake force; and a brake/drive forcecontrol section that requests the powertrain control section for thebrake/drive force and requests the brake control section for the brakeforce on the basis of the requested acceleration. The brake/drive forcecontrol section includes: a brake/drive force calculating section thatcalculates the requested brake/drive force acquired by converting therequested acceleration to a force; and a brake/drive force distributingsection that requests the powertrain control section for the requestedbrake/drive force, acquires the brake/drive force that is generated bythe powertrain in response to the request, and requests the brakecontrol section for the brake force corresponding to a differencebetween the requested brake/drive force and the acquired brake/driveforce when the requested brake/drive force is smaller than the acquiredbrake/drive force.

In order to solve the above problem, another aspect of the disclosure isa brake/drive force control system that controls a brake/drive force tobe generated by a powertrain including an engine and a brake force to begenerated by a brake, so as to maintain a target vehicle speed. Thebrake/drive force control system includes: a requested accelerationcalculating section that calculates requested acceleration asacceleration generated in the vehicle to maintain the target vehiclespeed; a powertrain control section that calculates a minimumbrake/drive force, which is a minimum brake/drive force capable of beinggenerated by the powertrain without executing a fuel cut of the engine,and a fuel-cut brake/drive force, which is the brake/drive forcegenerated by the powertrain through execution of the fuel cut, accepts arequest to generate the brake/drive force, and causes generation of therequested brake/drive force; a brake control section that accepts arequest to generate the brake force and causes the brake to generate therequested brake force; and a brake/drive force control section thatrequests the powertrain control section for the brake/drive force andrequests the brake control section for the brake force on the basis ofthe requested acceleration. The brake/drive force control sectionincludes: a brake/drive force calculating section that calculates therequested brake/drive force acquired by converting the requestedacceleration to a force; and a brake/drive force distributing sectionthat acquires the minimum brake/drive force and the fuel-cut brake/driveforce, when the requested brake/drive force is equal to or larger thanthe minimum brake/drive force, requests the powertrain control sectionfor the requested brake/drive force, when the requested brake/driveforce is smaller than the minimum brake/drive force and is larger thanthe fuel-cut brake/drive force, requests the powertrain for the minimumbrake/drive force, and requests the brake control section for the brakeforce corresponding to a difference between the requested brake/driveforce and the minimum brake/drive force, and when the requestedbrake/drive force is equal to or smaller than the fuel-cut brake/driveforce, requests the powertrain for the fuel-cut brake/drive force, andrequests the brake control section for the brake force corresponding toa difference between the requested brake/drive force and the fuel-cutbrake/drive force.

The disclosure can provide the brake/drive force control system capableof achieving preferred pursuance of the target vehicle speed andpreferred ride quality in the control for generating the brake/driveforce in the vehicle in order to maintain the target vehicle speed.

BRIEF DESCRIPTION OF THE DRAWINGS

Features, advantages, and technical and industrial significance ofexemplary embodiments of the disclosure will be described below withreference to the accompanying drawings, in which like numerals denotelike elements, and wherein:

FIG. 1 is a functional block diagram of a brake/drive force controlsystem according to first and second embodiments of the disclosure;

FIG. 2 is a sequence chart illustrating processing according to thefirst embodiment of the disclosure;

FIG. 3 includes graphs illustrating the processing according to thefirst and second embodiments of the disclosure;

FIG. 4 is a sequence chart illustrating processing according to thesecond embodiment of the disclosure; and

FIG. 5 includes graphs illustrating processing according to the relatedart.

DETAILED DESCRIPTION OF EMBODIMENTS

(First Embodiment) A brake/drive force control system according to afirst embodiment of the disclosure suppresses a fuel cut in the casewhere a requested brake/drive force is smaller than a brake/drive forcegenerated by a powertrain at the time of no fuel cut, but is larger thanthe brake/drive force generated by the powertrain during execution ofthe fuel cut. In addition, in the case where the brake/drive force insuch a range that cannot be generated only by the powertrain isrequested at the time of no fuel cut and during the execution of thefuel cut, a brake is made to generate a brake force, so as to match thebrake/drive force generated in the vehicle with the requestedbrake/drive force. In this way, the preferred pursuance to a targetvehicle speed and preferred ride quality without an abrupt change in thebrake/drive force can be achieved. A detailed description willhereinafter be made on this embodiment with reference to the drawings.

<Configuration> FIG. 1 is a functional block diagram of a brake/driveforce control system 1 according to this embodiment and peripheralequipment. The brake/drive force control system 1 includes a requestedacceleration calculating section 10, a brake/drive force control section20, a powertrain control section 30 that controls a powertrain 50, and abrake control section 40 that controls a brake 60.

The requested acceleration calculating section 10 is provided in adriver assistance system, such as ACC, that has a function of achievingand maintaining the target vehicle speed. On the basis of informationthat is acquired from a vehicle speed sensor, a camera, and the like andindicates a vehicle state and a peripheral state of the vehicle andinformation that is set in advance, the requested accelerationcalculating section 10 sets the target vehicle speed and calculates, ascontrol information for achieving and maintaining the target vehiclespeed, requested acceleration that is acceleration generated by thevehicle.

The brake/drive force control section 20 includes a brake/drive forcecalculating section 21 and a brake/drive force distributing section 22.The brake/drive force calculating section 21 accepts the above-describedrequested acceleration as a request from the requested accelerationcalculating section 10, converts the requested acceleration to a forceto be generated in the vehicle, and calculates a requested brake/driveforce. The requested brake/drive force is represented by a value, apositive direction of which is set to an advancing direction of thevehicle, for example. The requested brake/drive force can be calculatedon the basis of the requested acceleration and vehicle weight that isset in advance, for example. In addition, when calculating the requestedbrake/drive force, the brake/drive force calculating section 21 may alsocalculate feedback that is based on an actual vehicle speed acquiredfrom the vehicle speed sensor or the like, correction that is based onan inclination of a road surface and the like acquired from varioussensors, and the like. On the basis of the requested brake/drive force,the brake/drive force distributing section 22 requests the powertraincontrol section 30 for the brake/drive force that is either the brakeforce or the drive force, and further possibly requests the brakecontrol section 40 for the brake force.

The powertrain control section 30 controls the powertrain 50 provided inthe vehicle, and thus can generate the brake/drive force. The powertrain50 has an engine. When generating the brake force, the powertrain 50executes an engine fuel cut according to various states of thepowertrain 50, such as an engine temperature, and a value of the brakeforce. In addition, the powertrain control section 30 monitors thevarious states of the powertrain 50, and can calculate a minimumbrake/drive force and a fuel-cut brake/drive force. The minimumbrake/drive force is a minimum brake/drive force that can currently begenerated by the powertrain 50 without executing the fuel cut. Thefuel-cut brake/drive force is generated when the powertrain 50 currentlyexecutes the fuel cut. When generating the brake/drive force that isequal to or larger than the minimum brake/drive force, the powertrain 50does not execute the fuel cut. When generating the fuel-cut brake/driveforce, the powertrain 50 executes the fuel cut.

The brake control section 40 controls the brake 60 provided in thevehicle, and thus can generate the brake force.

<Processing> FIG. 2 is a sequence chart illustrating an example ofbrake/drive force control processing executed by the brake/drive forcecontrol system 1. A description will be made on the example of thebrake/drive force control processing with reference to FIG. 2. A flowillustrated in FIG. 2 is repeatedly executed during execution of adriver assistance function such as the ACC.

(Step S101): The requested acceleration calculating section 10calculates the requested acceleration as described above. In addition,the requested acceleration calculating section 10 notifies thebrake/drive force control section 20 of the requested acceleration.

(Step S102): The brake/drive force calculating section 21 of thebrake/drive force control section 20 accepts the requested accelerationnotified in step S101, and calculates the requested brake/drive force asdescribed above on the basis of the requested acceleration. In addition,the brake/drive force distributing section 22 of the brake/drive forcecontrol section 20 requests the powertrain control section 30 togenerate the requested brake/drive force.

(Step S103): The powertrain control section 30 accepts the requestedbrake/drive force requested in step S102, and determines the brake/driveforce to be generated by the powertrain 50 on the basis of the requestedbrake/drive force as follows. First, the powertrain control section 30calculates the minimum brake/drive force and the fuel-cut brake/driveforce described above.

(1-1) When the requested brake/drive force is larger than the fuel-cutbrake/drive force: the powertrain control section 30 causes thepowertrain 50 to generate larger one of the requested brake/drive forceand the minimum brake/drive force. In this case, the powertrain 50 doesnot execute the fuel cut.

(1-2) When the requested brake/drive force is equal to or smaller thanthe fuel-cut brake/drive force: the powertrain control section 30 causesthe powertrain 50 to generate the fuel-cut brake/drive force. In thiscase, the powertrain 50 executes the fuel cut as a result.

As described so far, the brake/drive force generated by the powertrain50 is equal to the requested brake/drive force or larger than therequested brake/drive force. That is, in the case where the requestedbrake/drive force is small and the brake force is further requested, thebrake force generated by the powertrain 50 is possibly insufficient forthe requested brake/drive force.

(Step S104): The powertrain control section 30 notifies the brake/driveforce control section 20 of the brake/drive force to be generated by thepowertrain 50 that is determined in step S103.

(Step S105): The brake/drive force distributing section 22 of thebrake/drive force control section 20 determines the brake force to begenerated by the brake 60 on the basis of the requested brake/driveforce and the brake/drive force to be generated by the powertrain 50,which is notified in step S104, as follows.

(1-3) When the requested brake/drive force is smaller than thebrake/drive force to be generated by the powertrain 50: the brake/driveforce distributing section 22 requests the brake control section 40 forthe brake force that corresponds to a difference between the requestedbrake/drive force and the brake/drive force to be generated by thepowertrain 50. That is, in the case where the requested brake/driveforce is small and thus the brake force is further requested, and thesufficient requested brake/drive force cannot be generated only by thepowertrain 50, the brake is actuated to compensate for shortage of thebrake force.

(1-4) When the requested brake/drive force is equal to the brake/driveforce to be generated by the powertrain 50: the brake/drive forcedistributing section 22 does not request the brake control section 40 togenerate the brake force. Alternatively, the brake/drive forcedistributing section 22 requests the brake control section 40 for 0 (N)as the brake force.

The powertrain control section 30 may acquire a range of the brakeforce, which can currently be generated by the brake, from the brakecontrol section 40, and may determine the requested brake force to thebrake control section 40 within the acquired range. For example, in(1-3) described above, in the case where an absolute value of the brakeforce corresponding to the difference between the requested brake/driveforce and the brake/drive force to be generated by the powertrain 50exceeds a maximum value of an absolute value of the brake force that cancurrently be generated by the brake, the brake/drive force distributingsection 22 may request the brake control section 40 for the brake forcecorresponding to such a maximum value.

(Step S106): The powertrain control section 30 causes the powertrain 50to generate the brake/drive force determined in step S103.

(Step S107): When being requested to generate the brake force from thebrake/drive force control section 20 in step S105, the brake controlsection 40 causes the brake 60 to generate the requested brake force.

The processing in steps S101 to S107 described so far is repeatedlyexecuted. A description will be made on an example of the brake/driveforce control by the above processing with reference to FIG. 3. FIG. 3includes graphs that have time in a horizontal axis and have, on avertical axis, an actual vehicle speed, the requested brake/drive force,and an actual brake/drive force. The actual brake/drive force generatedby the powertrain 50 is indicated by a bold broken line, and a total ofthe actual brake/drive force generated by the powertrain 50 and theactual brake force generated by the brake 60 is indicated by a boldsolid line.

In the example illustrated in FIG. 3, the above processing is initiatedat time T0. In order to achieve the target vehicle speed, the requestedbrake/drive force is gradually reduced, and at time T1, the requestedbrake/drive force becomes equal to the minimum brake/drive force.Thereafter, the requested brake/drive force becomes smaller than theminimum brake/drive force, at time T2, becomes equal to the fuel-cutbrake/drive force, and then becomes smaller than the minimum brake/driveforce. In FIG. 3, the examples of the target vehicle speed, the minimumbrake/drive force, and the fuel-cut brake/drive force are illustrated incombination. In FIG. 3, these forces are illustrated to have steadyvalues as the example. However, in reality, these forces possiblyfluctuate according to operation of the driver assistance system and thestate of the powertrain 50. The same processing can be executed evenwhen these values fluctuate.

A period in which time t is T0<t≤T1 corresponds to (1-1) and (1-4)described above. In this period, the powertrain control section 30causes the powertrain 50 to generate the requested brake/drive forcewithout executing the fuel cut, and the brake control section 40 doesnot cause the brake 60 to generate the brake force.

A period in which the time t is T1<t<T2 corresponds to (1-1) and (1-3)described above. In this period, the powertrain control section 30causes the powertrain 50 to generate the minimum brake/drive forcewithout executing the fuel cut, and the brake control section 40 causesthe brake 60 to generate the brake force corresponding to a differencebetween the requested brake/drive force and the minimum brake/driveforce.

When time at which the time t=T2 corresponds to (1-2) and (1-4)described above. At this time, the powertrain control section 30 causesthe powertrain 50 to execute the fuel cut and thereby generate thefuel-cut brake/drive force, and the brake control section 40 does notcause the brake 60 to generate the brake force.

A period in which the time t is T2<t corresponds to (1-2) and (1-3)described above. In this period, the powertrain control section 30causes the powertrain 50 to execute the fuel cut and thereby generatethe fuel-cut brake/drive force, and the brake control section 40 causesthe brake 60 to generate the brake force corresponding to a differencebetween the requested brake/drive force and the fuel-cut brake/driveforce.

As it has been described so far, in this embodiment, the powertrain 50and the brake 60 are cooperatively operated. As a result, thebrake/drive force generated in the vehicle can preferably match therequested brake/drive force.

(Second Embodiment) In the brake/drive force control system 1 accordingto the first embodiment, the powertrain control section 30 determinesthe brake/drive force to be generated by the powertrain 50. Meanwhile, abrake/drive force control system 1 according to a second embodiment ofthe disclosure has the same configuration as the brake/drive forcecontrol system 1 according to the first embodiment, but differstherefrom in a point that the brake/drive force control section 20determines the brake/drive force to be generated by the powertrain 50.

<Processing> FIG. 4 is a sequence chart illustrating an example of thebrake/drive force control processing executed by the brake/drive forcecontrol system 1. A description will be made on the example of thebrake/drive force control processing with reference to FIG. 4. The sameitems as those in the first embodiment will not be described or brieflybe described.

(Step S201): The requested acceleration calculating section 10calculates the requested acceleration and notifies the brake/drive forcecontrol section 20 of the requested acceleration.

(Step S202): The brake/drive force calculating section 21 of thebrake/drive force control section 20 calculates the requestedbrake/drive force on the basis of the requested acceleration.

(Step S203): The powertrain control section 30 calculates the minimumbrake/drive force and the fuel-cut brake/drive force, and notifies thebrake/drive force control section 20 of the minimum brake/drive forceand the fuel-cut brake/drive force. The processing in this step isprocessing that is periodically executed by the powertrain controlsection 30, for example. Thus, the brake/drive force control section 20can always acquire the minimum brake/drive force and the fuel-cutbrake/drive force.

(Step S204): On the basis of the requested brake/drive force calculatedin step S202 and the minimum brake/drive force and the fuel-cutbrake/drive force notified in step S203, the brake/drive forcedistributing section 22 of the brake/drive force control section 20determines the brake/drive force to be generated by the powertrain 50 asfollows, and requests the powertrain control section 30 for thebrake/drive force.

(2-1) When the requested brake/drive force is equal to or larger thanthe minimum brake/drive force: the brake/drive force distributingsection 22 requests the powertrain control section 30 for the requestedbrake/drive force.

(2-2) When the requested brake/drive force is smaller than the minimumbrake/drive force and is larger than the fuel-cut brake/drive force: thebrake/drive force distributing section 22 requests the powertraincontrol section 30 for the minimum brake/drive force.

(2-3) When the requested brake/drive force is equal to or smaller thanthe fuel-cut brake/drive force: the brake/drive force distributingsection 22 requests the powertrain control section 30 for the fuel-cutbrake/drive force.

(Step S205): On the basis of the requested brake/drive force calculatedin step S202 and the minimum brake/drive force and the fuel-cutbrake/drive force notified in step S203, the brake/drive forcedistributing section 22 of the brake/drive force control section 20determines the brake force to be generated by the brake 60 as follows.In the case where the brake force is generated, the brake/drive forcedistributing section 22 requests the brake control section 40 for thedetermined brake force.

(2-4) When the requested brake/drive force is equal to or larger thanthe minimum brake/drive force: the brake/drive force distributingsection 22 does not request the brake control section 40 to generate thebrake force. Alternatively, the brake/drive force distributing section22 requests the brake control section 40 for 0 (N) as the brake force.

(2-5) When the requested brake/drive force is smaller than the minimumbrake/drive force and is larger than the fuel-cut brake/drive force: thebrake/drive force distributing section 22 requests the brake controlsection 40 for the brake force corresponding to the difference betweenthe requested brake/drive force and the minimum brake/drive force.

(2-6) When the requested brake/drive force is equal to or smaller thanthe fuel-cut brake/drive force: the brake/drive force distributingsection 22 requests the brake control section 40 for the brake forcecorresponding to the difference between the requested brake/drive forceand the fuel-cut brake/drive force.

(Step S206): The powertrain control section 30 causes the powertrain 50to generate the brake/drive force requested in step S204. When therequested brake/drive force is larger than the fuel-cut brake/driveforce, the powertrain control section 30 causes the powertrain 50 togenerate the requested brake/drive force without executing the fuel cutas a result. Meanwhile, when the requested brake/drive force is equal toor smaller than the fuel-cut brake/drive force, the powertrain controlsection 30 causes the powertrain 50 to execute the fuel cut and therebygenerate the requested brake/drive force as a result.

(Step S207): When being requested to generate the brake force from thebrake/drive force control section 20 in step S205, the brake controlsection 40 causes the brake 60 to generate the requested brake force.

The processing in steps S201 to S207 described so far is repeatedlyexecuted. A result of the brake/drive force control by the processingdescribed so far is the same as that in the first embodiment. In orderto describe such a result of the brake/drive force control in the secondembodiment, a description will be made on an example of the brake/driveforce control by the processing in this embodiment with reference toFIG. 3.

The period in which the time t is 0<t≤T1 corresponds to (2-1) and (2-4)described above. In this period, the powertrain control section 30causes the powertrain 50 to generate the requested brake/drive forcewithout executing the fuel cut, and the brake control section 40 doesnot cause the brake 60 to generate the brake force.

The period in which the time t is T1<t<T2 corresponds to (2-2) and (2-5)described above. In this period, the powertrain control section 30causes the powertrain 50 to generate the minimum brake/drive forcewithout executing the fuel cut, and the brake control section 40 causesthe brake 60 to generate the brake force corresponding to the differencebetween the requested brake/drive force and the minimum brake/driveforce.

When the time at which the time t=T2 corresponds to (2-3) and (2-6)described above. At this time, the powertrain control section 30 causesthe powertrain 50 to execute the fuel cut and thereby generate thefuel-cut brake/drive force. In this case, the brake force correspondingto the difference between the requested brake/drive force and thefuel-cut brake/drive force is 0 (N). Thus, the brake control section 40does not cause the brake 60 to generate the brake force.

The period in which the time t is T2<t corresponds to (2-3) and (2-6)described above. In this period, the powertrain control section 30causes the powertrain 50 to execute the fuel cut and thereby generatethe fuel-cut brake/drive force, and the brake control section 40 causesthe brake 60 to generate the brake force corresponding to the differencebetween the requested brake/drive force and the fuel-cut brake/driveforce.

As it has been described so far, also in this embodiment, similar to thefirst embodiment, the powertrain 50 and the brake 60 are cooperativelyoperated. As a result, the brake/drive force generated in the vehiclecan preferably match the requested brake/drive force.

(Effects) According to each of the embodiments of the disclosure, in thecase where the requested brake/drive force is smaller than the driveforce generated by the powertrain at the time of no fuel cut, but islarger than the brake/drive force generated by the powertrain during theexecution of the fuel cut, the fuel cut is suppressed. In addition, inthe case where the requested brake/drive force is in such a range thatcannot be generated only by the powertrain at the time of no fuel cutand during the execution of the fuel cut, the brake is made to generatethe brake force, so as to match the brake/drive force generated in thevehicle with the requested brake/drive force. In this way, thebrake/drive force generated in the vehicle does not deviate from therequested brake/drive force for maintaining the target vehicle speed,and is not changed discontinuously due to the fuel cut. Therefore, thepreferred pursuance to the target vehicle speed and the preferred ridequality without the abrupt change in the brake/drive force can beachieved.

The description has been made so far on the embodiments of thedisclosure. However, the disclosure is not limited to the brake/driveforce control system but can be understood to include a control methodexecuted by each component of the brake/drive force control system and acomputer in each of the components, a control program, a non-transitorycomputer readable recording medium storing the control program, thevehicle on which the brake/drive force control system is mounted, andthe like.

The disclosure is useful for a brake/drive force system mounted on thevehicle and the like.

What is claimed is:
 1. A brake/drive force control system that controlsa brake/drive force to be generated by a powertrain including an engineand a brake force to be generated by a brake, so as to maintain a targetvehicle speed, the brake/drive force control system comprising: arequested acceleration calculating section that calculates requestedacceleration as acceleration generated in the vehicle to maintain thetarget vehicle speed; a powertrain control section that calculates aminimum brake/drive force, which is a minimum brake/drive force capableof being generated by the powertrain without executing a fuel cut of theengine, and a fuel-cut brake/drive force, which is the brake/drive forcegenerated by the powertrain through execution of the fuel cut, accepts arequest to generate the brake/drive force, causes the powertrain togenerate larger one of the requested brake/drive force and the minimumbrake/drive force when the requested brake/drive force is larger thanthe fuel-cut brake/drive force, and causes the powertrain to generatethe fuel-cut brake/drive force when the requested brake/drive force isequal to or smaller than the fuel-cut brake/drive force; a brake controlsection that accepts a request to generate the brake force and causesthe brake to generate the requested brake force; and a brake/drive forcecontrol section that requests the powertrain control section for thebrake/drive force and requests the brake control section for the brakeforce on the basis of the requested acceleration, wherein thebrake/drive force control section includes: a brake/drive forcecalculating section that calculates the requested brake/drive forceacquired by converting the requested acceleration to a force; and abrake/drive force distributing section that requests the powertraincontrol section for the requested brake/drive force, acquires thebrake/drive force that is generated by the powertrain in response to therequest, and requests the brake control section for the brake forcecorresponding to a difference between the requested brake/drive forceand the acquired brake/drive force when the requested brake/drive forceis smaller than the acquired brake/drive force.
 2. A brake/drive forcecontrol system that controls a brake/drive force to be generated by apowertrain including an engine and a brake force to be generated by abrake, so as to maintain a target vehicle speed, the brake/drive forcecontrol system comprising: a requested acceleration calculating sectionthat calculates requested acceleration as acceleration generated in thevehicle to maintain the target vehicle speed; a powertrain controlsection that calculates a minimum brake/drive force, which is a minimumbrake/drive force capable of being generated by the powertrain withoutexecuting a fuel cut of the engine, and a fuel-cut brake/drive force,which is the brake/drive force generated by the powertrain throughexecution of the fuel cut, accepts a request to generate the brake/driveforce, and causes generation of the requested brake/drive force; a brakecontrol section that accepts a request to generate the brake force andcauses the brake to generate the requested brake force; and abrake/drive force control section that requests the powertrain controlsection for the brake/drive force and requests the brake control sectionfor the brake force on the basis of the requested acceleration, whereinthe brake/drive force control section includes: a brake/drive forcecalculating section that calculates the requested brake/drive forceacquired by converting the requested acceleration to a force; and abrake/drive force distributing section that acquires the minimumbrake/drive force and the fuel-cut brake/drive force, when the requestedbrake/drive force is equal to or larger than the minimum brake/driveforce, requests the powertrain control section for the requestedbrake/drive force, when the requested brake/drive force is smaller thanthe minimum brake/drive force and is larger than the fuel-cutbrake/drive force, requests the powertrain for the minimum brake/driveforce, and requests the brake control section for the brake forcecorresponding to a difference between the requested brake/drive forceand the minimum brake/drive force, and when the requested brake/driveforce is equal to or smaller than the fuel-cut brake/drive force,requests the powertrain for the fuel-cut brake/drive force, and requeststhe brake control section for the brake force corresponding to adifference between the requested brake/drive force and the fuel-cutbrake/drive force.